Common Node Parameters
Common parameters are configuration options shared across multiple workflow nodes. These settings control output streaming, status messages, logging verbosity, and execution behavior when workflow paths converge.
These parameters appear in the Configuration Panel when a node is selected in the Workflow Designer. Not all parameters are available on all nodes parameter visibility depends on the node type.
Fixed And Expression Modes
Many common parameters support two input modes:
| Mode | Description |
|---|---|
| Fixed | Static value that remains constant during execution |
| Expression | Dynamic value using ${variable_name} syntax to reference workflow variables |
Expression mode enables dynamic configuration based on workflow state. For example, a streaming message can display Processing ${document_count} documents... where the count updates based on actual data.
Stream Output Response
This parameter controls whether the node sends its output to the chatbot interface for real-time streaming. When enabled, node results appear in the chatbot as they are generated. When disabled, the node processes silently without displaying output to the user.
Results are stored in workflow variables for downstream nodes regardless of this setting.
| Setting | Behavior |
|---|---|
| Enabled (default) | Node output streams to the chatbot in real-time |
| Disabled | Node processes silently; output is available only to downstream nodes |
Enabling is appropriate when a node produces content that users should see immediately, such as LLM responses, search results, or formatted data. This setting supports interactive chatbot experiences.
Disabling is appropriate when a node performs background processing such as data transformation or validation. This approach reduces chatbot clutter in workflows with many intermediate processing steps.
Note: Final output nodes typically have this setting enabled, while intermediate processing nodes have it disabled. This keeps chatbot responses focused on user-relevant information.
Streaming Messages
This parameter configures custom messages displayed in the chatbot before and after node execution. It appears only when Stream Output Response is enabled.
Both fields support variable interpolation with ${variable_name} syntax for dynamic content.
| Field | Description |
|---|---|
| Initial Message | Text shown when node execution begins |
| Completion Message | Text shown when node execution completes |
Examples:
- Initial:
Searching knowledge base...orProcessing ${document_count} documents... - Completion:
Search completeorFound ${result_count} results
Streaming messages provide status updates for long-running operations and set user expectations about node activity.
Logging Mode
This parameter controls logging verbosity for debugging and tracing workflow execution. Logging captures node execution details, parameter values, and processing steps.
| Mode | Description |
|---|---|
| All (default) | Full logging of node execution, parameters, and processing steps |
| None | Logging is skipped for this node |
The All setting is typically appropriate for development and testing environments where detailed execution traces are valuable. The None setting is typically appropriate for non-critical nodes in production to reduce log volume and storage requirements.
Wait For All Edges
This parameter controls execution behavior when multiple workflow paths converge at a single node. It determines whether the node waits for all incoming connections or executes as each connection arrives.
| Setting | Behavior |
|---|---|
| Enabled (default) | Waits for all incoming edges to complete before executing once |
| Disabled | Executes each time any incoming edge arrives, potentially running multiple times |
Enabling is required when a node needs data from multiple upstream branches to function correctly. This includes synchronization points in parallel workflows (fan-in pattern) and result aggregation from multiple processing paths.
Disabling is appropriate when a node needs data from only one upstream path. This applies to conditional convergence where branches are mutually exclusive, such as after IF or Switch nodes.
Note: Parallel fan-in patterns where all branches must complete require this setting to be enabled. Conditional convergence in IF, Switch, or Loop scenarios where only one path executes requires this setting to be disabled.
Output Field
This parameter specifies the workflow variable where the node stores its output data. If the variable does not exist, it is created automatically.
Examples:
llm_response— stores LLM node output for downstream nodessearch_results— stores search results for conditional processingprocessed_data— stores transformed data for the next workflow step
Descriptive variable names make workflow logic easier to understand and maintain. The stored value can be referenced in downstream nodes using ${variable_name} syntax.
Input Field
This parameter specifies the workflow variable from which the node reads its input data. The variable must exist in the workflow state before execution.
Examples:
${user_query}— reads the original user input from the User Prompt node${extracted_text}— reads text extracted by an upstream processing node${api_response}— reads data retrieved from an HTTP node
The variable selector in the Configuration Panel displays available variables from the current workflow state.